fix(codecompanion): compatibility with v19#276
Conversation
|
Seems like a straightforward patch. Would love to see this merged! |
|
I tried to temporarily switch to this branch but got problems with the mcphub binary download so a fast merge would be very much appreciated. |
If you're using Lazy then you can use https://github.com/polirritmico/lazy-local-patcher.nvim plus save the patch file into your Neovim config to get patched MCPHub. |
That's a real handy workaround. I'll have a look into this. Thanks for pointing that out! Update: The with the content: diff --git a/lua/mcphub/extensions/codecompanion/variables.lua b/lua/mcphub/extensions/codecompanion/variables.lua
index 2a15a55..20c7e14 100644
--- a/lua/mcphub/extensions/codecompanion/variables.lua
+++ b/lua/mcphub/extensions/codecompanion/variables.lua
@@ -14,7 +14,7 @@ function M.register(opts)
return
end
- local cc_variables = config.interactions.chat.variables
+ local cc_variables = config.interactions.chat.editor_context
-- Remove existing MCP variables
for key, value in pairs(cc_variables) do |
|
Replaced by #279. |
mcphub.nvim currently crashes on startup with CodeCompanion v19 because CodeCompanion renamed chat variables to editor_context. The upstream reports are ravitemer/mcphub.nvim#275 and ravitemer/mcphub.nvim#278. PR ravitemer/mcphub.nvim#276 was closed in favor of #279. #279 is still open and not merged, so use the upstream-recommended temporary workaround, make_vars = false. This keeps MCP tools and slash commands enabled, but disables MCP resources as CodeCompanion # context until the upstream v19 compatibility patch lands.
* chore(nvim): update APIs for 0.12 * fix(nvim): skip write autocmds for special buffers * chore(mise): add textlint tools * fix(nvim): disable mcphub vars for codecompanion v19 mcphub.nvim currently crashes on startup with CodeCompanion v19 because CodeCompanion renamed chat variables to editor_context. The upstream reports are ravitemer/mcphub.nvim#275 and ravitemer/mcphub.nvim#278. PR ravitemer/mcphub.nvim#276 was closed in favor of #279. #279 is still open and not merged, so use the upstream-recommended temporary workaround, make_vars = false. This keeps MCP tools and slash commands enabled, but disables MCP resources as CodeCompanion # context until the upstream v19 compatibility patch lands. * chore(mise): remove default npm packages
3 participants
Description
Fixes compatibility with CodeCompanion v19.
Related Issue(s)
Fixes #275
Screenshots
Checklist
make testto ensure all tests passmake formatto format the codemake docsto update the vimdoc pages